home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
vfx301.zip
/
VERIFIX.DOC
< prev
next >
Wrap
Text File
|
1992-01-19
|
43KB
|
1,029 lines
V E R I F I X
Call Back Verifier for Wildcat! 3.x+ BBSs
Version 3.01
(c) 1990, 1991, 1992
By Sophisticated Software
ALL RIGHTS RESERVED
Support System
Sophisticated Software BBS
(215)968-4998
FidoNET 1:273/215
EchoNET 50:5215/215
Baud: 38400/19200/9600/2400/1200 V.42
ACKNOWLEDGMENTS
ACKNOWLEDGMENTS
The following tools are used in creating and maintaining
VERIFIX:
Compiler: Microsoft C 6.0A
Libraries: CXL graphics library (Mike Smedley), MCOMM
serial I/O library
Editors: Brief (Solution Systems)
Documentation:Microsoft Word for Windows 2.0
CONTACTING SOPHISTICATED SOFTWARE
You can contact Sophisticated Software at the following
address:
By mail:
Sophisticated Software
P.O. Box 55
Newtown, PA 18940-0055
Electronically:
BBS Support:(215) 968-4998, Newtown, PA, at 1200 to
38400 Baud, 24 hours a day, no parity, 8 data bits, 1
stop bit.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 2
Table of Contents
ACKNOWLEDGMENTS ..........................................2
CONTACTING SOPHISTICATED SOFTWARE ........................2
DISCLAIMER ...............................................4
SHAREWARE ANNOUNCEMENT ...................................4
INTRODUCTION .............................................4
FEATURES .................................................5
INSTALLATION .............................................7
Creating Optional Files .............................9
Display Files .......................................11
CARRIER LOSS .............................................13
MISCELLANEOUS ............................................13
Log Files ...........................................13
Local Mode ..........................................14
Special Applications ................................15
MULTI NODE USAGE .........................................15
Environment Variables ...............................15
Log Files ...........................................17
UPGRADING USERS ..........................................17
USER SUPPORT .............................................18
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 3
DISCLAIMER
DISCLAIMER
Sophisticated Software hereby disclaims all warranties
relating to this product, whether expressed or implied,
including without limitation any implied warranties of
merchant ability or fitness for a particular purpose.
Sophisticated Software cannot and will not be liable for any
special, incidental, consequential, indirect or similar
damages due to loss of data or any other reason, even if
Sophisticated Software or an authorized Sophisticated
Software agent has been advised of the possibility of such
damages. In no event shall the liability for any damages
ever exceed the price paid for the license to use software,
regardless of the form and/or extent of the claim. The user
of this program bears all risk as to the quality and
performance of the software.
SHAREWARE ANNOUNCEMENT
VERIFIX is a fully functional SHAREWARE product. It is NOT
free and it is NOT in the public domain. If, after
evaluating the program for 90 days, you find it to be useful
enough to use it on a regular basis, you are expected to pay
for it by registering with Sophisticated Software. The
registration fee is $20.00. The registered .KEY file shall
NOT be distributed. The registered version will let you
create custom screens, and display your BBS name in the
opening screen.
To become a registered user after the 90 day demonstration
period, just print the ORDER.FRM included with this ZIP
file. After we receive your check / money order WE WILL
POST a REGISTERED KEY file on the SUPPORT BBS within 24
hours. You will be notified on your next log in by a
message from the author what the name of the keyfile is and
the password needed to download it. The registered KEY will
work with all present and future versions of VERIFIX. There
is only a one time fee. Each new version of VERIFIX can be
downloaded from the support BBS or the CATHOUSE BBS
(Mustang's HQ BBS).
INTRODUCTION
VERIFIX was created for the Wildcat! 3.x+ System Operator.
Many BBS systems have lots of new users call every day.
Wouldn't it be nice to see if the user on the other side of
the modem is really who they say they are? Well, now you
can! With VERIFIX! This program will automatically call
back the user and "verify" him / her in less then 2 minutes.
Speaking of 2 minutes, that is about how long it takes to
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 4
FEATURES
set up this "door". Once set up, VERIFIX runs by itself,
unattended, and working very hard for you.
It is a "hands-off" approach to automatically verify new or
existing users. This will put an end to lengthy voice
calls, and make you sleep better at night knowing that the
names in your Wildcat! database are "real" people. VERIFIX
will automatically upgrade the user to a verified level that
you specify. Our goal was to keep the program,
configuration, and ease of use as simple as possible, but
still maintain complete flexibility and functionality.
This program is the ultimate in functionality. It has
everything you need to verify users and more! From
operating on non-standard comm ports, supporting up to
115,200 baud, multi-node and single node operation in the
same package, DESQview AND Windows aware, incoming call
(collision) protection, writing the newuser a nice message
for his next log in, specifying a non-callback time,
selective long distance call back, and writing all activity
to both Wildcat!'s activity.xxx log and VERIFIX's own log
files!
FEATURES
o Compatible with Wildcat! 3.x+.
o Automatically upgrades the user to the verified
status of your choice.
o Multiple upgrade levels.
o Will add more time to that user for that session. You
specify how much time to add, or none at all.
o Will write its log files in any directory you
specify.
o A "congratulations on your upgrade" screen is shown
to the user on his next log in. SysOp draws the screen
he wants to be displayed.
o Has multi-area code capability. This feature is
useful for people that have more than 1 local area
code.
o Collision (incoming call) protection. VERIFIX sends
a friendly message to the incoming caller to tell him a
verification is in progress.
o Long distance protection. You specify if long
distance call back is allowed.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 5
FEATURES
o Single node AND full multi-node operation in ONE
program.
o Has a "local" mode when ran from the DOS prompt so
registered users can test their color or mono screens.
o Has a "local" mode when run from Wildcat!
o You can specify a time range that VERIFIX will NOT
call out to verify users.
o Written in 100% Microsoft C 6.0A. No BRUN modules!
o Supports locked baud rates up to 115,200 baud, Com1,
Com2, Com3, Com4 (ANSI standard addresses).
o Supports NON-STANDARD communication ports. Will read
the Wildcat! .MDM file for modem info.
o Easy to setup configuration file using the editor
VCONFIG.
o Re-validation protection.
o Checks user entered area code against a SysOp defined
areacode.bad file for protection.
o Checks user entered prefix against a SysOp defined
prefix.bad file for protection.
o Creates log files to show exactly what the user has
done. Also writes to the Wildcat! ACTIVITY.### log of
that node.
o SysOp can create customized screens, both ANSI and
ASCII. Registered version.
o Monitors carrier. Will recover if new user drops
carrier inside of VERIFIX.
o Selective long distance calling.
o Windows and DESQview aware. Will give time slices
back to multitasker while waiting for keypress.
o Hitting ESCape key terminates the verification
process.
o License Key concept. Gives you a 90 day evaluation
period.
o Free software updates available electronically.
o 24 hour Support BBS.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 6
INSTALLATION
INSTALLATION
The following files are included in the .ZIP:
DOOR1.BAT......Sample Bat File.
VERIFIX.EXE....Executable File.
VERIFIX.CFG....Sample Config File.
VERIFIX.DOC....This File.
VERIFIX.HIS....History file (ALWAYS READ!).
VCONFIG.EXE....EDITOR used to create the .CFG file.
VCONFIG.HLP....The Help file for VCONFIG.
ORDER.FRM......Order form to be printed.
README.1ST.....Important info not in this .DOC file.
BLDNBS.EXE.....Generates a VERIFIED.NBS file.
Installation is simple, if you follow these directions:
1. Before installation BACKUP your system. Sophisticated
Software will not be responsible for any loss of data.
2. Place all the files from the diskette into the sub
directory that you will be running the door from. i.e.
D:\WC30\DOOR\VERIFIX
3. Create the VERIFIX.CFG file using the included editor
VCONFIG. When using VCONFIG and you aren't sure about a
field, simply press the F1 key. It is context sensitive,
which means whatever field you are in, it will give you help
for THAT field. Below is a "printout" of what VCONFIG will
create.
Naturally VCONFIG doesn't put the information on the right
in the .cfg file. This is here now to show you what each
line does.
Contents of a VERIFIX.CFG file
Ed <-- #1 SysOp's first name.
Blazejewski <-- #2 SysOp's last name.
SS BBS <-- #3 Your BBS name.
D:\WC30 <-- #4 Directory of NODE HOME files.
Y <-- #5 Call Long Distance Y/N.
T <-- #6 Tone or Pulse T/P.
215,609 <-- #7 SysOp's LOCAL Area Codes.
NEWUSER <-- #8 New User Security level.
9, <-- #9 Additional Dialing prefix or NO.
VERIFIED <-- #10 Verified Security level.
N <-- #11 Hang Up after verified LONG DISTANCE?
Y <-- #12 Hang up after verified locally?
20 <-- #13 Minutes to add for this session.
D:\WC30\VERIFIX<-- #14 Directory to write the log files.
30 <-- #15 Seconds for Local Callback timeout.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 7
INSTALLATION
60 <-- #16 Seconds for Long Distance Callback
timeout.
2400-0600 <-- #17 Range of time to NOT verify people.
Y <-- #18 Should friendly message be sent
The NODE HOME directory is where both the WILDCAT.EXE
resides, and your activity.### log file is written.
In line number 7, if you live in an area that has MORE THAN
ONE LOCAL AREA CODE, you enter all local area codes here.
They MUST be separated by a comma. You can enter up to 4
local area codes. If you only have 1 local area code where
you live, just enter it here. Don't really worry about this
field, VCONFIG will take care of it for you.
Line number 9 in the config file. This is useful for an
office or special environment. If you need to dial a
[9,] to get out of your PBX, here is were you insert
that additional code. Also, you can insert your 1-800
long distance number, then your long distance code, if
you have a calling card. You can also enter modem
command strings.
i.e. M0L1,18005551212,,194875210
The above string will be sent to the modem first, before the
caller's phone number. IF YOU DON'T USE THIS OPTION, enter
a NO
Line 11 will drop carrier on the new user if he/she is
calling long distance and you specify a Y here. Remember,
if you select N here, you will pay the long distance bill
because your system called theirs.
Line 12 will drop carrier on the new user if he/she is
calling locally and you specify a Y here.
In line 13, if the user was validated, this field will add
the specified time in minutes to that users account. An
example of this is you give first time callers only 10
minutes on-line. By the time they fill out the
questionnaire and look around, they probably went through
about 7 minutes. That only leaves 3 minutes left for the
day. If the user runs through VERIFIX and becomes
validated, VERIFIX will add the specified minutes to his /
her time on-line for that session. In the example .cfg
file shown above, I am adding 20 extra time to the users
account.
In line 17, you type in the range of time, in MILITARY TIME,
you do NOT want VERIFIX to call back. In this example, I
don't want VERIFIX calling out from 12:00 midnight until 6
in the morning. At 6:01 in the morning, VERIFIX will start
calling back again.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 8
INSTALLATION
4. Run the BLDNBS.EXE file in the VERIFIX subdirectory.
This will search your ALLUSERS.DAT file and extract all the
phone numbers except the numbers from the security level you
specify. Typing BLDNBS NEWUSER or BLDNBS WC1 will write all
phone numbers to the VERIFIED.NBS file EXCEPT the ones from
the security level you specified on the command line.
5. Create a DOOR1.BAT, or what ever the door number is you
plan on using, in the node home directory. Use an ASCII text
editor like Brief editor, or PC Magazine's TED. It should
look like this:
ECHO OFF
cd \wc30\door\verifix
VERIFIX
The above batch file will work if you have Wildcat! setup to
run in SWAP mode.
ECHO OFF
cd \wc30\door\verifix
VERIFIX
cd \wc30
cat.bat
The above batch file will work if you are NOT shelling to
run doors.
Creating Optional Files
Here is a list of file names you can create to "fine tune"
VERIFIX. Theses files are not needed, but ARE recommended.
Each on will be explained below.
AREACODE.BAD
PREFIX.BAD
AREACODE.CAL
AREACODE#.NBS
USER#.BBS/.SCR
AREACODE.BAD -- Create an ASCII text file called
AREACODE.BAD and insert the area codes you do NOT want to
call no matter what!
Example:
201
516
911
555
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 9
INSTALLATION
Make sure that every number is on a different line. Do NOT
use ranges of numbers like 201-210. This will not work.
PREFIX.BAD -- Create an ASCII text file called PREFIX.BAD
and insert the prefixes you do NOT want to call no matter
what!
Example:
555
911
Make sure that every number is on a different line.
The AREACODE.BAD and PREFIX.BAD files are for your
protection. This way the caller will not have YOUR system
call the police or directory assistance! It is not necessary
to create AREACODE.BAD and PREFIX.BAD files; but if found,
VERIFIX will use them. Make sure that the *.BAD files you
create are in the VERIFIX directory.
AREACODE#.NBS - Create an ASCII text file called 215.NBS
(optional). In other words, this file name is YOUR AREA CODE
with a .nbs file extension!!! An example is if you live in
an area where your PRIMARY area code is say 918, then the
file name is 918.NBS, it's that easy. This will tell
VERIFIX the LOCAL EXCHANGES in your area. VERIFIX will
compare the user entered prefix to all the prefixes found in
the 215.NBS file. If a match is found, VERIFIX will call
that user, because he/she is a local call. If your long
distance flag is set to Y in the VERIFIX.CFG file, then the
creation of 215.NBS is not needed, because VERIFIX will call
everyone, regardless if he/she is long distance or not.
EXAMPLE: my 215.NBS file (only these local prefixes will be
called)
/ Philadelphia exchanges local to me /
968
349
919
/ Suburb exchanges local to me /
829
485
128
Note: Notice in the above example I used comments to
seperate the groups of prefixes. Make sure that NO numbers
are used in the comment. The comment is helpful so that you
know what exchanges match what location.
VERIFIX will append to a file called VERIFIED.NBS each time
it is run. In this file is a list of all the phone numbers
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 10
INSTALLATION
that the new users have been verified at. VERIFIX reads
this file to determine if the user has already been called.
The phone number in the door.sys file will be written into
VERIFIED.NBS. If the user enters a different number than
in the door.sys file, this number AND the door.sys phone
number will be written into VERIFIED.NBS.
Example: If the user originally tells Wildcat! that his
phone number is 215-123-4567, but he/she is verified at 215-
765-4321 it will write BOTH numbers into the VERIFIED.NBS
file, and also write this information to the log files for
your records.
AREACODE.CAL - This is also an ASCII text file. If you have
VERIFIX configured to NOT call back long distance, but this
file is present, it will ONLY call the area codes that you
have placed in this file. For example, say you live in the
215 area code and have VERIFIX configured for NO long
distance call back. But you create the AREACODE.CAL file
and put in it 609. VERIFIX will not call back long
distance, except it will call long distance into the 609
area code. Again, this is used for selective long distance
call back.
USER#.BBS/.SCR - You create both the USER#.BBS (mono) file
and the USER#.SCR (color) file. Leave these files in the
VERIFIX subdirectory. If you choose to use this option, it
must be selected as a Y in the VCONFIG field. This is how
it works; if the user gets validated, VERIFIX checks his
user number, and makes the appropriate USER# file in the
Wildcat! display subdirectory. Lets say that John Smith, a
new user, logs in and becomes verified. He happens to be
record number 567 in the Wildcat! database. VERIFIX will
then copy your templates over to the files USER567.SCR and
USER567.BBS in your display directory. The next time John
Smith logs in, he will read that friendly welcome message.
After reading this Wildcat! WILL AUTOMATICALLY DELETE the
files USER567.SCR and USER567.BBS.
Display Files
The following files are DISPLAY screens that you can create
if you do not like the default screens. In previous
versions of VERIFIX, CALLBACK.BBS was displayed when VERIFIX
called back the user, the user's modem picked up the phone,
and there was a carrier. THIS screen has been changed to
WELCOME.BBS and WELCOME.SCR. Please make a note of that.
*WELCOME.BBS -- MONO screen first displayed when VERIFIX
calls the user back. It should say something like "Welcome
back to Sophisticated Software BBS".
*WELCOME.SCR -- ANSI screen explained above.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 11
INSTALLATION
*BYE.BBS -- MONO good-bye screen.
*BYE.SCR -- ANSI good-bye screen.
*VERIFIED.BBS -- MONO screen displayed when the user has
successfully been verified.
*VERIFIED.SCR -- ANSI screen displayed when the user has
successfully been verified.
*NOTVALID.BBS -- MONO screen displayed when user fails
verification.
*NOTVALID.SCR -- ANSI screen displayed when user fails
verification.
*NOTNEW.BBS -- MONO screen displayed when an already
verified AND upgraded user accesses VERIFIX.
*NOTNEW.SCR -- ANSI screen displayed when an already
verified AND upgraded user accesses VERIFIX.
*BENCALED.BBS -- MONO screen displayed when a verified but
NOT upgraded user accesses VERIFIX.
*BENCALED.SCR -- ANSI screen displayed when a verified but
NOT upgraded user accesses VERIFIX.
*NOLOC-PF.BBS -- MONO screen displayed when the user enters
a prefix that is out of YOUR dialing range.
*NOLOC-PF.SCR -- ANSI screen described above.
*NOLOC-AC.BBS -- MONO screen displayed when the user enters
an area code that is out of YOUR dialing range.
*NOLOC-AC.SCR -- ANSI screen described above.
*CALLUSER.BBS -- MONO screen that is displayed to the user
after they enter a phone number. This screen has
instructions on what to do during call back. Like for them
to type in ATA or ATS0=1 to pick up the phone.
*CALLUSER.SCR -- ANSI screen described above.
*TOOLATE.BBS -- MONO screen that is displayed when the user
tries to become verified in a time that matches your NON
callback time. Example, if a no call back time is from 3:00
am to 6:00 am and the user enters VERIFIX at 4:00 am, this
screen will be displayed.
*TOOLATE.SCR -- ANSI screen described above.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 12
CARRIER LOSS
NOTE: the * before the filenames mean that it is
available in the registered version.
CARRIER LOSS
VERIFIX will sense loss of carrier and will shut itself down
and return back to the bbs software on its own. You can run
a Watchdog program if it makes you feel better, but it is
not needed. VERIFIX will also write to the activity that
carrier loss was detected.
MISCELLANEOUS
VERIFIX will knows if it is running under DESQview or
Windows. If either one is detected, it will give back time
slices to the multitasker at all "press a key" prompts, and
delays. Also, if DESQview is found, VERIFIX will write all
screen displays to the DESQview video buffer instead of
directly to the screen. This will preven screen bleed
through into other DESQview windows.
VERIFIX also interprets modem return codes, therefore during
call back, if VERIFIX gets a busy signal it will end that
call and try again.
Log Files
VERIFIX writes its own activity logs in the directory that
you specified in the configuration file; it also writes to
the Wildcat! activity log file. The name of the file
VERIFIX writes to are VALIDYES.xxx and VALIDNO.xxx. The xxx
are for node numbers. If you run a single line version, the
.001 will replace the .xxx. If you are running a multi-node
version, then the long file extension can be as high as
.250. I run 1 modem line node and 1 local node, therefore
my log files will look like this:
VALIDYES.001 Validated user list on node 1
VALIDYES.002 Validated user list on node 2
VALIDNO.001 Failed validation user list on node 1
VALIDNO.002 Failed validation user list on node 2
VALIDYES.xxx
------------
This file is written if a new user successfully completes
the verification process. It writes the following to the
log file:
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 13
MISCELLANEOUS
1. Users Name.
2. Time verified.
3. Date verified.
4. If the number dialed is different from WILDCAT!
database number.
5. If there was an incoming call during
verification.
VALIDNO.xxx
-----------
This file is written if a new user fails the verification
process for any of the following reasons.
1. Security level too high or too low. (not new
user)
2. No answer after 3 tries.
3. Wrong Password.
4. Dropped Carrier.
5. Unacceptable area code and prefix entered (as
defined by the SysOp).
6. The call was long distance and you are not
verifying long distance callers.
7. Calling in a "NO VERIFY" time period.
VERIFIX also writes the above information to the Wildcat!
activity.### log file. If you run a single node, then
VERIFIX will write to the activity.001 file. It will track
the user, and append his/her actions to the activity.001
file. If you run a multi-node version of Wildcat!, VERIFIX
will write to activity.002 if node 2 is used. It is
important to have SET WCNODEID=2 in your cat.bat file.
This tells VERIFIX what log to write to.
Local Mode
VERIFIX NOW has the ability to run in the local mode. All
carrier checking is turned off, and there is no actual
callback. This is particularly helpful when registered
users want to check their custom screens before going "on
line". To start VERIFIX in local mode with color screens
displayed, simply type VERIFIX LOCAL at the DOS prompt. If
you want to display mono screens, then start VERIFIX in the
local mode by typing VERIFIX LOCAL MONO. Another way to
test VERIFIX locally is to start Wildcat! locally, then
execute the door that runs VERIFIX. This time it will read
your DOOR.SYS and USERINFO.DAT files. Your name and
password will appear at the bottom of the screen. When
finished, and you entered the correct password, VERIFIX will
even upgrade you to the level specified in the .cfg file.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 14
MULTI NODE USAGE
One quick note; when running VERIFIX from the DOS prompt,
there are no userinfo.dat or door.sys files present.
VERIFIX substitutes the name and password field as Master
SysOp and VFX_TEST.
Special Applications
Having read this document, you now know the operation of
VERIFIX, and all the files VERIFIX uses and manipulates. If
you have a special application, like verifying users, but
not upgrading them, or verifying EVERY user on EVERY call,
this is how it can be done.
Start VCONFIG. In the field New User Level #1 type SYSOP
and in the Upgrade Level #1 also type SYSOP. Now when level
SYSOP runs through VERIFIX, if he/she passes validation,
VERIFIX will upgrade the SYSOP level to SYSOP, or no upgrade
will take place. The user is already at the SYSOP level!
If you need to verify users at EVERY call, then you must
delete the verified.nbs file every time. If VERIFIX finds
the phone number in verified.nbs it will not continue to
validate. It will give the message that the user has
already been upgraded. So, in your door1.bat or whatever
door you run just cd\wc3\door\verifix then del verified.nbs
then run verifix. Now you can verify up to 3 levels of
security on every call.
Another situation would be if John Smith calls in and gets
verified. VERIFIX will write his number to the verified.nbs
file. Now John's wife calls in, Sally. Sally Smith tries
to get validated, but VERIFIX already finds the phone number
in the verified.nbs file. To accomidate this, registered
users can create a NOTNEW.SCR and NOTNEW.BBS file explaining
that the phone number has already been called, but for the
user to please leave a note to the SysOp regarding this
situation.
MULTI NODE USAGE
Environment Variables
VERIFIX can successfully be run in a multi-node
configuration. Here are the steps needed:
1. Make sure that you have the SET WCNODEID= environment
variable set in your catx.bat file. This is extremely
important!
2. Set a VERIFIX environment variable in each of your
nodes's cat.bat file. This tells VERIFIX to override the
default settings found in the VERIFIX.CFG file. If no SET
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 15
MULTI NODE USAGE
variable is found, VERIFIX will use what is in the .cfg
file.
Here is a list of environment variables that VERIFIX reads
if present:
SET VFXLD=
SET VFXTP=
SET VFXDROPLOCAL=
SET VFXDROPLD=
SET VFXMORETIME=
SET VFXLOGPATH=
SET VFXVERIFYTIME=
SET WCMDM=
SET WCBASEID=
SET WCIRQID=
Some examples of setting the variables:
SET VFXLD=Y or SET VFXLD=N. This overrides the long
distance yes no configuration file directive.
SET VFXTP=T or SET VFXTP=P. This tells verifix to dial with
a tone or pulse.
SET VFXDROPLOCAL=Y or SET VFXDROPLOCAL=N. This tells
verifix to drop or not to drop carrier with a local call
back connection.
SET VFXDROPLD=Y or SET VFXDROPLD=N. This tells verifix to
drop or not to drop carrier when your call back was long
distance connection. If N was chosen, then the caller will
stay on-line. Remember it is long distance so you pay the
phone bill.
SET VFXMORETIME=20 or how much extra time you want to give
the new user when they became validated.
SET VFXLOGPATH=D:\WC3\MYLOGS or whatever drive and directory
you wish to store the VALIDYES.xxx and the VALIDNO.xxx log
files.
SET VFXVERIFYTIME=0300-0600 this is the range of time, in
MILITARY time, that VERIFIX will NOT verify people. In this
example, VERIFIX will not call back people from 3:00 A.M. to
6:00 A.M. This is handy when you have mischievous people
calling your bbs and typing in the wrong number at 3 o'clock
in the morning. Then VERIFIX would call that number, hence
waking up someone.
SET WCMDM you set this environment variable if your modem
settings are different for each node. VERIFIX will read
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 16
UPGRADING USERS
this file and open the port specified using the IRQ and BASE
id found in your .MDM file.
SET WCBASEID if this variable is found, and no WCMDM
variable is found, VERIFIX will open up the comm port at
this hexidecimal address.
SET WCIRQID if this variable is found, and no WCMDM variable
is found, VERIFIX will open up the comm port using this
custom IRQ.
Log Files
If using a multi-node version of Wildcat!, VERIFIX will
write to its logfile.node and to the activity.node files.
For example, if there is a caller on node 18, then the files
ACTIVITY.018 and VALIDYES.018 or VALIDNO.018 will be written
to.
UPGRADING USERS
VERIFIX does NOT write to the Wildcat! databases, per se, it
changes information in the userinfo.dat file. When Wildcat!
is started up after returning from the door, it will re-read
the info found in this file and then write to its database.
What can be more safer than having Wildcat! write to its own
database!
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 17
USER SUPPORT
USER SUPPORT
If you have any questions, problems or suggestions we would
like to hear from you. The latest version of VERIFIX can
be had from the following BBS:
Sophisticated Software BBS
(215) 968-4998
24 Hours
Fidonet 1:273/215
*HST* 9600 Baud V.42
Thanks for your continued support!
Ed Blazejewski.
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 18
Index
2 NOTNEW.BBS, 12
215.NBS, 10 NOTNEW.SCR, 12
NOTVALID.BBS, 12
A NOTVALID.SCR, 12
AREACODE.BAD, 9
AREACODE.CAL, 9 P
PREFIX.BAD, 9
B
BENCALED.BBS, 12 R
BENCALED.SCR, 12 registered user, 4
BLDNBS.EXE, 9
BYE.BBS, 12 S
BYE.SCR, 12 selective long distance
call back, 11
C SET VFXDROPLD=, 16
CALLUSER.BBS, 12 SET VFXDROPLOCAL=, 16
CALLUSER.SCR, 12 SET VFXLD=, 16
CARRIER LOSS, 13 SET VFXLOGPATH=, 16
Creating Optional Files, 9 SET VFXMORETIME=, 16
SET VFXUPGRADE=, 16
D SET VFXVERIFYTIME=, 16
DESQview, 13 SET WCBASEID, 16
DISCLAIMER, 4 SET WCIRQID, 16
Display Files, 11 SET WCMDM, 16
DOOR1.BAT, 9 SHAREWARE, 4
SHAREWARE ANNOUNCEMENT, 4
E support, 4
Environment Variables, 15 SWAP mode, 9
F U
FEATURES, 5 USER SUPPORT, 18
USER.BBS, 11
I USER.SCR, 11
INSTALLATION, 7
INTRODUCTION, 4 V
VCONFIG, 7
L VERIFIED.BBS, 12
LOCAL AREA CODE, 8 VERIFIED.SCR, 12
local mode, 14
Log Files, 13 W
Windows, 13
M
MULTI NODE USAGE, 15
N
NOLOC-AC.BBS, 12
NOLOC-AC.SCR, 12
NOLOC-PF.BBS, 12
NOLOC-PF.SCR, 12
_________________________________________________________________
Copyright (c) Sophisticated Software - VERIFIX Manual Page 19